I agree entirely - it is clearly not necessary for an SMTP MTA to be announced anywhere as a mail exchanger for a spammer to try and use it for
third party spam. An interesting example is documented here.
What I am talking about here is
first party spam - i.e. a spammer trying to deliver spam messages directly to recipients inside your own domain - so called direct-to-MX spam.
And the message is clear from my findings - as any chain is a strong as its weakest link, so any policy to reject spam based on RBL or other criteria derived from originating IP or envelope is only as good as your mail exchanger with the weakest policy settings.
Like you, a single MX is not for me, so I run two -
but with identical RBL and other local policy settings.